feat: add governed continuity, authenticated RLS, and recovery runtime - #1
feat: add governed continuity, authenticated RLS, and recovery runtime#1jstar0 wants to merge 377 commits into
Conversation
W35 authenticated remote Web Chat qualificationRepository evidence is now committed at head Protected delivery
Exact-head deployment recheck
The full W35 trajectory remains |
|
I08 Linux package repository qualification is complete and retained as public evidence.
Evidence:
Boundary: this qualifies ephemeral CI repository signing and exact local repository bundles. It does not claim a stable production signing key, public hosted repository, mirrors, retention, cross-version lifecycle, tagged publication, or RPM payload signatures. |
|
Current PR head revalidation is complete.
|
I09 Linux repository lifecycle qualificationThe cross-version repository lifecycle is now evidence-closed on the implementation head and requalified on the final documentation head.
Retained failure history remains visible in run 29958102641: attempt 1 was cancelled during the published GitHub hosted-runner delay incident; attempt 2 exposed the Evidence: Claim boundary: this qualifies one frozen DEB/APT and RPM/DNF base-to-candidate lifecycle on native AMD64/ARM64: normal upgrade, no implicit downgrade, explicit rollback, normal re-upgrade, removal, source binding, state preservation, service dormancy, metadata-signature enforcement, and credential-free evidence. It does not qualify a stable production repository key, public hosted repository, mirrors or retention SLA, unattended updates, release tags or public version promises, database migration/rollback, RPM payload signatures, or the complete platform. I09 bundles gate signing but are not presented as release payloads; the signed release manifest remains 16 entries. |
|
I10 external withheld-evaluation protocol qualification is complete.
The repository now has strict submission v1, submission-bound attestation v2, CLI create/verify surfaces, public schemas, positive and negative controls, the frozen I10 case, and machine-checked evidence. The status is deliberately |
I11 macOS authenticated service lifecycle qualificationImplementation source
The preceding Evidence is committed at head Final evidence-head delivery:
Claim boundary remains narrow: no database down migration, arbitrary historical rollback, zero-downtime or long-duration SLA, model-quality claim, public exposure, notarization, system-wide installation, or new real-client qualification from the backend probes. |
Scope
This Draft PR carries the complete Vermory implementation and evidence history
from the independent
jstar0/Vermoryrepository into the canonicalsamekind/Vermoryorganization repository.It includes PostgreSQL-authoritative workspace and conversation continuity,
thin Global Defaults, governed bridges, MCP/Web Chat/OpenClaw/Hermes clients,
formation and review loops, RLS/authentication, retrieval projections,
operations/recovery profiles, reality cases, benchmark evidence, release
packaging, GitHub OIDC keyless artifact signing, and repository collaboration
governance.
Product Boundary
Defaults remain isolated by default.
Migration Provenance
https://github.com/jstar0/Vermoryhttps://github.com/jstar0/Vermory/pull/13eb0c2af900d71d96963c0f5264ce9ed8c5025492fe75531c7d8e85b6d7fadf39e2b42dd70ebaac7The original PR body exceeds GitHub's current 65,536-character creation limit.
Its complete 83,911-byte body is retained below as ordered migration comments.
Repository evidence documents remain the authoritative detailed records.
Current Delivery
The latest source head previously passed protected
testandsign-snapshotchecks in the original repository. The new organization PR must pass those
checks again under the
samekind/Vermoryworkflow identity before merge.This PR remains draft. It requires a non-author review under the organization
repository's protected-branch policy.